-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
validator/client: process Sync Committee roles separately #13995
validator/client: process Sync Committee roles separately #13995
Conversation
In a DV context, to be compatible with the proposed selection endpoint, the VC must push all partial selections to it instead of just one. Process sync committee role separately within the RolesAt method, so that partial selections can be pushed to the DV client appropriately, if configured.
59ddd60
to
f0f12ec
Compare
Force pushed in order to update git username/email, new computer :^) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello! Thanks for the PR and congrats on the new computer :)
Where are the test changes? This PR does not build.
Weird, I did run the test suite on my machine and it seemed to run just fine? Will double-check and fix all the outstanding issues. |
Found a bug in the impl! Fixing as we speak. |
Process sync committee duty at slot boundary as well.
@prestonvanloon should be fixed now! |
Hey @gsora , thanks a lot for the contribution! A PR got merged in the meantime causing a conflict. Can you please resolve it? The main point of the conflict and my change request is to not return errors from role assignments if possible because that will affect all roles/validators. We should only log an error and continue, if possible. |
…the list ignore the duty and continue
# Conflicts: # validator/client/validator.go
Head branch was pushed to by a user without write access
thank you so much for this PR |
657750b
What type of PR is this?
Bug fix
What does this PR do? Why is it needed?
In a DV context, to be compatible with the proposed selection endpoint, the VC must push all partial selections to it instead of just one.
Process sync committee role separately within the RolesAt method, so that partial selections can be pushed to the DV client appropriately, if configured.
Which issues(s) does this PR fix?
No issue open for this issue as of now, as it has been detected during internal testing.
Other notes for review